User definable on-line co-user lists

ABSTRACT

A real time notification system that tracks, for each user, the logon status of selected co-users of an on-line or network system and displays that information in real time to the tracking user in a unique graphical interface. The invention provides user definable on-line co-user lists, or “buddy lists”, that track specific co-users in real-time automatically. A user can create many separate buddy lists of co-users, either with intersecting or disjoint lists of users, and label these buddy lists according to the user&#39;s preference. The user can update a buddy list or create new buddy lists whenever necessary. When a user logs on to a system, the user&#39;s set of buddy lists is presented to the buddy list system. The buddy list system attempts to match co-users currently logged into the system with the entries on the user&#39;s buddy list. Any matches are displayed to the user. As co-users logon and logoff, a user&#39;s buddy list is updated to reflect these changes. An indication can also be added to show that a co-user just logged on or just left the system.

BACKGROUND

1. Field of the Invention

This invention relates to on-line communication networks, andparticularly to interpersonal communications on such networks.

2. Description of Related Art

An important aspect of an “online” system, such as the proprietarysystem operated by America Online, Inc, (AOL) or the public Internetsystem, is knowledge of the people/users/processes on that system and amethodology for communicating with them through some selected protocol.When a person “logs on” to a network system, they are in effectidentifying themselves to the system and announcing their presence. Onmost systems, this presence is unique to every user who is on thesystem. For example, on the AOL network this presence is known as the“screen name”, but on other systems it could be an Internet Protocol(IP) address or some other unique identifier.

An Internet Service Provider (ISP) is, in a sense, an online systembecause every user has an associated IP network address and may alsohave a user id and password. There can also be a hierarchy of logonsystems, where an ISP is used to connect to a first network, and thenonce connected the user can log on to another system with a differentidentity. These secondary systems can be in parallel (i.e., a userconnects to an ISP and then logs on to multiple systems), or acombination of parallel and hierarchical (i.e., a user logs on tomultiple systems in parallel once connected to the ISP, and then fromone of those parallel systems logs on to yet other systems. Thousands tomillions of users may be accessing such complex networks at any point intime.

A problem with networks on any size is tracking personal relationshipsand maintaining knowledge of the people/users/processes on that system.In the AOL network, a user could use a LOCATE function to inquire fromthe system if another user was currently logged into the system. In theCompuServe network, a user can use a more limited “WHO'S HERE” functionto determine who is present in a forum conference.

The present invention addresses the problem of tracking personalrelationships and maintaining knowledge of the people/users/processes onthat system with a unique way of establishing and maintaining userdefinable on-line co-user lists.

SUMMARY

The invention implements a real time notification system that tracks,for each user, the logon status of selected co-users of an on-line ornetwork system and displays that information in real time to thetracking user in a unique graphical interface. The invention providesuser definable on-line co-user lists, or “buddy lists”, that trackspecific co-users in real-time automatically.

A user can create many separate buddy lists of co-users, either withintersecting or disjoint lists of users, and label these buddy listsaccording to the user's preference. The user can update a buddy list orcreate new buddy lists whenever necessary. When a user logs on to asystem, the user's set of buddy lists is presented to the buddy listsystem. The buddy list system attempts to match co-users currentlylogged into the system with the entries on the user's buddy list. Anymatches are displayed to the user. As co-users logon and logoff, auser's buddy list is updated to reflect these changes. An indication canalso be added to show that a co-user just logged on or just left thesystem.

The details of the preferred embodiment of the present invention are setforth in the accompanying drawings and the description below. Once thedetails of the invention are known, numerous additional innovations andchanges will become obvious to one skilled in the art.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram of a typical network system 10 in which theinvention can be implemented.

FIG. 2 a is a set of symbolic data records showing the basic types ofdata used by one embodiment of the invention for a buddy list, and theconceptual relationship of data elements.

FIG. 2 b is a set of symbolic data records showing the basic types ofdata used by one embodiment of the invention for a permissions list, andthe conceptual relationship of data elements.

FIG. 3 is a graphical display of one implementation of the invention,showing a buddy list window.

FIG. 4 is a graphical display of one implementation of the invention,showing a buddy list setup window.

FIG. 5 is a graphical display of one implementation of the invention,showing a buddy list create window.

FIG. 6 is a graphical display of one implementation of the invention,showing a buddy list preferences window.

FIG. 7 is a graphical display of one implementation of the invention,showing a search member directory window.

FIG. 8 is a graphical display of one implementation of the invention,showing a member location window.

FIG. 9 is a graphical display of one implementation of the invention,showing an instant message window.

FIG. 10 is a graphical display of one implementation of the invention,showing a buddy chat window.

FIG. 11 is a flowchart showing an implementation of the invention.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Throughout this description, the preferred embodiment and examples shownshould be considered as exemplars, rather than as limitations on thepresent invention.

Overview

The invention implements a real time notification system that tracks,for each user, the logon status of selected co-users and displays thatinformation in real time to the tracking user in a unique graphicalinterface. The invention provides user definable on-line co-user lists,or “buddy lists”, that track specific co-users in real-timeautomatically. Such automatic monitoring is significant, because in asystem of any size there would be no way for a user to track the comingsand goings of thousands or millions of users each moment in time.

An important component of the buddy list system is that a user cancreate many separate buddy lists of co-users, either with intersectingor disjoint lists of co-users, and label these buddy lists according tothe user's preference. The user can update a buddy list or create newbuddy lists whenever necessary. When a user logs on to a system, theuser's set of buddy lists is presented to the buddy list system. Thebuddy list system attempts to match co-users currently logged into thesystem with the entries on the user's buddy list. Any matches aredisplayed to the user. As co-users logon and logoff, a user's buddy listis updated in real-time (or near real-time, taking into account networkand processing delays) to reflect these changes. An indication can alsobe added to show that a co-user just logged on or just left the system.

Hardware System

By way of example only. FIG. 1 is a block diagram of a typical networksystem 10 in which the invention can be implemented. The network system10 includes a plurality of user stations 12 that preferably include aprocessor chassis 14 having a network link. The network link is forreceiving and transmitting data in analog or digital form over acommunications link 16, such as a serial link, local area network,wireless link, parallel link, etc. Also coupled to a typical processorchassis 14 is a display 18, a keyboard 20, and a pointing device 22(e.g., a mouse).

The communications link 16 couples each user station 12 as a “client” toa logon system 24, which is typically a software program executing on aremote server somewhere on a network. The logon system 24 communicateswith a “Buddy List System” 26, which is preferably a software programexecuting on a server somewhere on the network. The Buddy List. System26 maintains a database 28 for storing user information. The database 28may be of any type, such as relational or hierarchical, and may becentralized or distributed. For example, the database 28 may be storedat least in part on each user's own station 12. In such a case, thedatabase 28 contents would be transmitted to the Buddy List System 26when the user logged into the system.

Data Structure

FIG. 2 a is a set of symbolic data records showing the basic types ofdata used by the Buddy List System 26, and the conceptual relationshipof data elements. A Group Name table 30 stores user-defined group namesfor buddy lists. Each user may define multiple buddy lists by groupnames (two being shown by way of example). Each group name in the GroupName table 30 has an associated Buddy List table 32, comprising multiplerecords. Each Buddy List table 32 record corresponds to a co-user(“buddy”) that the user wishes to track. In the preferred embodiment,the record includes data elements for the screen name (or address, suchas an Internet address) of a particular co-user to be tracked, and thelogon status of that user (e.g., codes for “In” or “Out”).

FIG. 2 b is a set of symbolic data records showing the basic types ofdata used by one embodiment of the invention for a Permissions List 34,and the conceptual relationship of data elements. Each user in thesystem has an associated Block Status code. If a user's Block Statuscode is equivalent to “none”, then no co-user may enter that user intothe co-user's buddy lists. If a user's Block Status code is equivalentto “all”, then all co-users may enter that user into their buddy lists.If a user's Block Status code is equivalent to “all except”, then allco-users except those entered in a linked Exclusion List 36 may enterthat user into their buddy lists. If a user's Block Status code isequivalent to “none except”, then only co-users entered in a linkedInclusion List 38 may enter that user into the co-user's buddy lists. Inone embodiment, a user may only have one of an inclusion List 36 and anExclusion List 48.

Example Implementation

FIG. 3 is a graphical display of one implementation of the invention,showing a Buddy List window 40 with a buddy list named “Home List” in alarge scrollable area. Buddy list names are like categories. Other buddylists can be shown in the same display. Indented underneath each buddylist are the names (or addresses) of user-selected co-users comprisingthat list. In the example shown, the “Home List” includes three co-usersand their status as “IN” (i.e., currently logged into the system) or“OUT” (i.e., currently logged out of the system). Any desired method ortechnique cart be used to indicate log status, such as distinctattributes (e.g., bolding a name to indicate logged in, graying a nameto indicated logged out) or other symbols (e.g., checkmarks to indicatelogged in), etc. In still another embodiment, only logged in members ofa buddy list are displayed. In one embodiment, an asterisk or othersymbol appears next to the screen name of the most recent co-user to loginto the system, and parentheses are placed around the screen name ofthe most recent co-user to log out of the system.

In the preferred embodiment, a user can “minimize” a buddy list tosuppress display of all the co-users in that group. This is preferablyimplemented so that a double click on the buddy list name will cause allthe screen names listed beneath to disappear. In the preferredembodiment, minimized buddy lists are indicated by a “+” symbol next tothe buddy list name. Double-clicking on the buddy list name againdisplays all of the hidden co-users under that name. A user can alsokeep tabs on each list by checking out the numbers posted in parenthesisnext to the buddy list names. This number tells the user how many peopleon that list are logged in out of the total number of screen names onthe buddy list. In the illustrated example, ⅔ means that two of thethree people on the “Home List” are currently online.

In tire preferred embodiment, when the user first logs into the system,the Buddy List window 40 opens, informing the user which of the user'sbuddy list members are currently online. The user can either close thiswindow, or leave it open while visiting other areas of the system. Ifthe Buddy List window 40 is left open, the user has a current, real-timelist of all the user's buddies in who are online at any particularmoment.

The illustrated Buddy List window 40 shows a number of buttons forsetting up or using buddy lists. Included buttons in the preferredembodiment are: LOCATE, for determining which “chat room” a buddy is inat a particular moment; IM, for sending an “Instant Message”; SETUP, forcreating and editing buddy lists or setting buddy list preferences; andBUDDY CHAT, for inviting buddies to a private chat or a favorite placein the system.

Setup

FIG. 4 is a graphical display of one implementation of the invention,showing a Buddy List Setup window 50 with a buddy list named “Home List”in a scrollable area. Buttons are provided for creating a new buddylist; editing a selected buddy list; deleting a buddy list; viewing themembers of a selected buddy list; accessing a Member Directory for thesystem; and accessing a preferences windows. In the preferredembodiment, each buddy list is shown in the scrollable area with a countof the number of co-users in each list.

FIG. 5 is a graphical display of one implementation of the invention,showing a Buddy List Create window 60. A user can enter a buddy listgroup name and a screen name for each co-user to be tracked. A list ofbuddies on a particular list are also displayed, along with a buttonallowing removal of an existing buddy. After entry of all necessary datain such a window, the user's Group Name table 30 and the appropriateBuddy List table 32 are updated using conventional data processingtechniques. Editing a buddy list can be done from the same or a similarwindow.

FIG. 6 is a graphical display of one implementation of the invention,showing a Buddy List Preferences window 70. In the preferred embodiment,these Preferences include the following:

-   -   Show me my Buddy List(s) immediately after I sign onto AOL. This        option opens the Buddy List window 40 (FIG. 3) when the user        logs on to the system.    -   Play sound when buddies sign-on. This option enables a sound to        play when one of the co-users on a user's buddy list program        logs on (“BuddyIn”).    -   Play sound when buddies sign-off. This option enables a sound to        play when one of the co-users on a user's buddy list program        logs off (“BuddyOut”).    -   Allow all members to add me to their lists/invitations. This        option grants permission for all co-users to add the user to        their buddy lists and send the user “Buddy Chat Invitations” and        other information. If set, the appropriate user record in the        Permissions List table 34 is marked with a code for “all” in the        Block Status field.    -   Block all members from adding me to their lists/invitations.        This option restricts all co-users from adding the user to their        buddy lists and from sending the user “Buddy Chat Invitations”        and other information. If set, the appropriate user record in        the Permissions List table 34 is marked with a code for “none”        in the Block Status field.    -   Allow only the members below. This option restricts all members        from adding the user to their buddy lists and from sending the        user “Buddy Chat Invitations” and other information, except for        those co-users specifically listed where provided in the window.        If set, the appropriate user record in the Permissions List        table 34 is marked with a code for “none except” in the Block        Status field, and an Inclusion List 38 is linked to the user for        storing the names of included co-users.    -   Block only the members below. This option grants permission for        all other members to add the user to their buddy lists and send        the user “Buddy Chat Invitations” and other information, except        for those co-users specifically listed where provided in the        window. If set, the appropriate user record in the Permissions        List table 34 is marked with a code for “all except” in the        Block Status field, and an Exclusion List 36 is linked to the        user for storing the names of excluded co-users.    -   Sound Library. Allows a user to select sound events for        “BuddyIn” and “BuddyOut”.

In the preferred embodiment, the Inclusion List 38 and the ExclusionList 36 options are mutually exclusive. In this way, a user can controlwho sees the user logging on and off the system. Although the user canbe placed on the buddy list of a co-user, if the user blocks visibilitythrough the use of these controls, the co-user does not see thelogon/logoff status of that user.

FIG. 7 is a graphical display of one implementation of the invention,showing a Search Member Directory window 80. In the preferredembodiment, this feature is accessed from the Buddy List Setup window 50(FIG. 4), and allows searching a system directory in known fashion forscreen names or addresses of co-users, for entry into buddy lists.

Locate

FIG. 8 is a graphical display of one implementation of the invention,showing a member location window 90. In the preferred embodiment, thisfeature is accessed from the Buddy List window 40 (FIG. 3). Selecting aco-user's name from a buddy list and activating the LOCATE button willcause the system to determine whether the selected co-user is in a chatarea or not. If no co-user is selected and the LOCATE button isactivated, a member location window 90 is displayed with the input fieldblank, for entry of a co-user name. This feature using the existinglocate functions of the system.

Instant Messages

Once a co-user is displayed on a user's buddy list, indicating that theco-user is currently logged into the network system, the preferredembodiment of the invention enables a simple way of communicating withthat co-user. FIG. 9 is a graphical display of one implementation of theinvention, showing an Instant Message window 100. In the preferredembodiment, the Instant Message window is automatically displayed byactivating (e.g., by clicking or double clicking) a co-user's name on abuddy list. The “To:” line of the window is pre-filled with the selectedco-user's name and the cursor is positioned in the text entry area readyfor text to be typed to be sent to the targeted co-user. The InstantMessage function can also be activated by highlighting a co-user name inthe buddy list and clicking on the IM button in the Buddy List window 40(FIG. 3).

Buddy Chat

FIG. 10 is a graphical display of one implementation of the invention,showing a Buddy Chat window 110. As implemented on the AOL on-linesystem, the Buddy Chat function can be used to send an invitation to oneor more co-users to a private “chat room” or a favorite place in thesystem. In the preferred embodiment, this function can be initiated byselecting a co-user name and activating the BUDDY CHAT button in theBuddy List window 40 (FIG. 3). The Buddy Chat window 110 is displayed,allowing the user to add additional names to the Screen Names to Invitefield either manually or by selecting additional names from the BuddyList window 40 and again activating the BUDDY CHAT button. A message canbe sent to each invitee via the Message to Rend field. In the preferredembodiment, an entire buddy list group can be added to the Buddy Chatwindow 110 by selecting a group name from the Buddy List window 40 andactivating the BUDDY CHAT button or double-clicking.

To talk privately with the selected co-users, the user selects thePrivate Chat Room radio button and enters a “Buddy Chat Room Name” inthe provided edit box. If the edit box is left blank, a Buddy Chat RoomName is automatically created for the user. Upon selecting Send, eachselected co-user will receive a message inviting them to access anddisplay a Buddy Chat Room (chat rooms are an existing feature of the AOLsystem).

To share those places a user likes best on the AOL system, the userselects the Keyword/Favorite Place radio button and enters a “Keyword”(i.e., a shortcut word defining an address) to a system site in theprovided edit box, either manually or by using a “drag and drop” actionfrom a list of the user's favorite places in the system. Upon selectingSend, each selected co-user will receive a message inviting them toaccess and display that online site.

FIG. 11 is a flowchart showing an implementation of the invention. AUser logs in to a Logan System in conventional fashion (Step 200). TheLogon System performs normal logon procedures (e.g., requesting a userID and/or a password) and notifies the Buddy List System about the User(i.e., passes the User's ID, address, or screen name to the Buddy ListSystem) (Step 202). The Buddy List System accesses that User's BuddyLists from a database, which may be, for example, on the user's station12 (Step 204). The entries in the User's Buddy Lists are then comparedto the records of the Logan System (Step 206). This step is shown indotted outline to indicate that the comparison can be done by passingrecords from the Logon System to the Buddy List System, or vice versa,or could be done a separate system. The Buddy List System then displaysa Buddy List window showing the status (i.e., logged in or not) of theco-users on the User's Buddy Lists with any of various indicatormarkings (Step 208).

Thereafter, while the User's Buddy List window is open, the Logon Systemnotifies the Buddy List System about new logons/logoffs of co-users(Step 210), causing a new compare of the User's Buddy List entries tothe Logon System records (Step 206). Again, the compare may be performedanywhere. For example, the Logon System may maintain a copy of a User'sBuddy Lists, and notify the Buddy List System only upon a logon statuschange for a co-user on the User's Buddy Lists. The Buddy List Systemthen updates the indicated status of the displayed co-users (Step 208).

Software Implementation

The invention may be implemented in hardware or software, or acombination of both. However, preferably, the invention is implementedin computer programs executing on programmable computers each comprisingat least one processor, at least one data storage system (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. Program code is applied toinput data to perform the functions described herein and generate outputinformation. The output information is applied to one or more outputdevices, in known fashion.

Each program is preferably implemented in a high level procedural orobject oriented programming language to communicate with a computersystem. However, the programs can be implemented in assembly or machinelanguage, if desired. In any case, the language may be a compiled orinterpreted language.

Each such computer program is preferably stored on a storage media ordevice (e.g., ROM or magnetic diskette) readable by a general or specialpurpose programmable computer, for configuring and operating thecomputer when the storage media or device is read by the computer toperform the procedures described herein. The inventive system may alsobe considered to be implemented as a computer-readable storage medium.configured with a computer program, where the storage medium soconfigured causes a computer to operate in a specific and predefinedmanner to perform the functions described herein.

A number of embodiments of the present invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing; from the spirit and scope of the invention. Forexample, while the preferred embodiment is event driven, meaning thatupdates to a buddy list are based on to change in the logon status ofall co-users or of the selected co-users on a user's buddy list, updatescan instead be performed on a periodic basis, where the buddy listsystem polls the logon system for logon status changes, or vice versa.Accordingly, it is to be understood that the invention is not to belimited by the specific illustrated embodiment, but only by the scope ofthe appended claims.

What is claimed is:
 1. A method for permitting a user of an electronicnetwork system to track the logon status of selected co-users of suchsystem, comprising the steps of: (a) associating an identification listof selected co-users with the user; (b) accessing the user'sidentification list; (c) comparing the selected co-users on user'sidentification list to logon records for such selected co-usersmaintained by a logon system; (d) indicating to the user the logonstatus of the selected co-users on the user's identification listaccording to such logon records; and (e) repeating steps (c) and (d)under any of the following conditions: (1) periodically; or (2) afterany change in the logon status of co-users of the system; or (3) afterany change in the logon status of the selected co-users on the user'sidentification list; thereby tracking the logon status of selectedco-users of such system.
 2. The method of claim 1, wherein the step ofcomparing is performed by the logon system.
 3. The method of claim 1,wherein the user's identification list is stored at least in part on theuser's station.
 4. The method of claim 1, wherein steps (b), (c), and(d) are initially performed when the user logs on to the system.
 5. Themethod of claim 1, further including the step of permitting the user toselectively block which co-users can add the user to identificationlists for such co-users.
 6. The method of claim 5, wherein the user'sblock selections are stored in a permissions list, and the user'spermissions list is stored at least in part on the user's station. 7.The method of claim 1, further including the step of permitting the userto transmit a communication to at least one co-user on the user'sidentification list having a logged on status.
 8. A computer program,residing on a computer-readable medium, for permitting a user of anelectronic network system to track the logon status of selected co-usersof such system, and comprising instructions for causing a computer to:(a) associate an identification list of selected co-users with the user:(b) access the user's identification list; (c) compare the selectedco-users on user's identification list to logon records for suchselected co-users maintained by a logon system; (d) indicate to the userthe logon status of the selected co-users on the user's identificationlist according to such logon records; and (e) repeat functions (c) and(d) under any of the following conditions: (1) periodically; or (2)after any change in the logon status of co-users of the system; or (3)after any change in the logon status of the selected co-users on theuser's identification list; thereby tracking the logon status ofselected co-users of such system.
 9. The computer program of claim 8,wherein the compare is performed by the logon system.
 10. The computerprogram of claim 8, wherein the user's identification list is stored atleast in part on the user's station.
 11. The computer program of claim8, wherein functions (b), (c), and (d) are initially performed when theuser logs on to the system.
 12. The computer program of claim 8, whereinthe instructions further cause the computer to permit the user toselectively block which co-users can add the user to identificationlists for such co-users.
 13. The computer program of claim 12, whereinthe user's block selections are stored in a permissions list, and theuser's permissions list is stored at least in part on the user'sstation.
 14. The computer program of claim 8, wherein the instructionsfurther cause the computer to permit the user to transmit acommunication to at least one co-user on the user's identification listhaving a logged on status.